…draft-core

… for iOS linking

Navigation stack is captured when feedback is triggered, before the
Updraft UI covers the app. Apps using single-activity navigation
(Compose Navigation, Navigation Component) can plug their library in
via Updraft.navigationStackProvider; the platform default reports the
activity stack (Android) or view controller chain (iOS). Also fixes
the package filter that swallowed host activities whose package merely
shares the com.appswithlove.updraft prefix, like the sample app.

The legacy iOS SDK never used shake detection; its feedback trigger was
UIApplicationUserDidTakeScreenshotNotification. The accelerometer-based
shake also cannot work on the simulator (no accelerometer), so shake
appeared broken there. Both triggers are now active on iOS: screenshot
(all environments, legacy parity) and shake (physical devices).

Shake reaches iOS apps as a responder-chain motion event, not as
accelerometer data, so the CMMotionManager detector never fired on the
simulator and required nothing in the responder chain to consume the
event on devices. The SDK now swizzles UIWindow.motionEnded:withEvent:
at start, calling through to the original implementation. The IMP is a
staticCFunction rather than a Kotlin lambda: block bridging would
marshal the NSInteger motion argument as an object and crash.

…items

…esting)

The repo stays and becomes the single home for Android + iOS: root
project renamed to updraft-sdk, POM name/URLs point at the new repo
slug, README repositions the SDK as Kotlin/Compose Multiplatform and
notes that updraft-sdk-ios is superseded. GitHub-side rename and
archiving updraft-sdk-ios remain manual release-time steps.

…rsions

Publishing previously ran no tests: a bad push to production would ship
broken artifacts that Maven Central cannot replace. The job now runs
the full build plus iOS simulator tests first, fails fast if the
version is already tagged, publishes under a 'maven-central' GitHub
environment (protection rules can be added in settings), and uses the
maintained softprops/action-gh-release instead of the archived
actions/create-release. JDK unified to 17 to match CI.

The SDK is built with Kotlin 2.2 / CMP 1.9: Kotlin Android consumers
need >= 2.1 (metadata n+1 rule), KMP/CMP consumers >= 2.2, Java-only
and XCFramework consumers are unaffected. The README lists the exact
compile-time errors older projects will see and the fix.

The legacy SDK fetched strings from Loco into Android res/; Compose
Multiplatform resources use the same strings.xml format, so updateLoco
now writes into updraft-ui-compose commonMain composeResources and both
platforms share the result. The API key moves from the build file
(exposed in git history — rotate it) to local.properties.

Restores the legacy 'Released 3 weeks ago. You're currently on version
X.' message using kotlin.time (no new dependency). Buckets: just now
under an hour, then hours/days/weeks/months/years plurals. The plurals
live in plurals.xml so updateLoco, which only rewrites strings.xml,
cannot clobber them. Falls back to the previous message when create_at
is missing or unparseable.

KMP migration M2: iOS support, device verification round, CMP rebrand